[INFO] fetching crate hypermangle-py 0.2.0...
[INFO] testing hypermangle-py-0.2.0 against try#0abe69e6c16114311cc2700e972492e64d69c28f for pr-154065-1
[INFO] extracting crate hypermangle-py 0.2.0 into /workspace/builds/worker-6-tc2/source
[INFO] started tweaking crates.io crate hypermangle-py 0.2.0
[INFO] finished tweaking crates.io crate hypermangle-py 0.2.0
[INFO] tweaked toml for crates.io crate hypermangle-py 0.2.0 written to /workspace/builds/worker-6-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate hypermangle-py 0.2.0 on toolchain 0abe69e6c16114311cc2700e972492e64d69c28f
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+0abe69e6c16114311cc2700e972492e64d69c28f" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+0abe69e6c16114311cc2700e972492e64d69c28f" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]      Locking 158 packages to latest compatible versions
[INFO] [stderr]       Adding axum v0.6.20 (available: v0.8.8)
[INFO] [stderr]       Adding generic-array v0.14.7 (available: v0.14.9)
[INFO] [stderr]       Adding pyo3 v0.19.2 (available: v0.28.2)
[INFO] [stderr]       Adding pyo3-asyncio v0.19.0 (available: v0.20.0)
[INFO] [stderr]       Adding tokio v1.30.0 (available: v1.50.0)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+0abe69e6c16114311cc2700e972492e64d69c28f" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+0abe69e6c16114311cc2700e972492e64d69c28f" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 4b8926d385d4920da3bd7b04b171a78c251d801f4d0ca2c936fedefaf5058249
[INFO] running `Command { std: "docker" "start" "-a" "4b8926d385d4920da3bd7b04b171a78c251d801f4d0ca2c936fedefaf5058249", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "4b8926d385d4920da3bd7b04b171a78c251d801f4d0ca2c936fedefaf5058249", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "4b8926d385d4920da3bd7b04b171a78c251d801f4d0ca2c936fedefaf5058249", kill_on_drop: false }`
[INFO] [stdout] 4b8926d385d4920da3bd7b04b171a78c251d801f4d0ca2c936fedefaf5058249
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+0abe69e6c16114311cc2700e972492e64d69c28f" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 3cecbd1be65ab260256e7a410067230380ab00c9a5ad171ebd4a2950936198af
[INFO] running `Command { std: "docker" "start" "-a" "3cecbd1be65ab260256e7a410067230380ab00c9a5ad171ebd4a2950936198af", kill_on_drop: false }`
[INFO] [stderr]    Compiling target-lexicon v0.12.16
[INFO] [stderr]    Compiling smallvec v1.15.1
[INFO] [stderr]    Compiling futures-sink v0.3.32
[INFO] [stderr]    Compiling slab v0.4.12
[INFO] [stderr]    Compiling zerocopy v0.8.48
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling serde_core v1.0.228
[INFO] [stderr]    Compiling mio v0.8.11
[INFO] [stderr]    Compiling http v0.2.12
[INFO] [stderr]    Compiling socket2 v0.5.10
[INFO] [stderr]    Compiling num_cpus v1.17.0
[INFO] [stderr]    Compiling getrandom v0.2.17
[INFO] [stderr]    Compiling tracing-core v0.1.36
[INFO] [stderr]    Compiling serde v1.0.228
[INFO] [stderr]    Compiling thiserror v1.0.69
[INFO] [stderr]    Compiling axum-core v0.3.4
[INFO] [stderr]    Compiling futures-channel v0.3.32
[INFO] [stderr]    Compiling pin-project-internal v1.1.11
[INFO] [stderr]    Compiling serde_json v1.0.149
[INFO] [stderr]    Compiling rand_core v0.6.4
[INFO] [stderr]    Compiling futures-util v0.3.32
[INFO] [stderr]    Compiling data-encoding v2.10.0
[INFO] [stderr]    Compiling tokio v1.30.0
[INFO] [stderr]    Compiling icu_normalizer v2.1.1
[INFO] [stderr]    Compiling parking_lot_core v0.9.12
[INFO] [stderr]    Compiling axum v0.6.20
[INFO] [stderr]    Compiling http-body v0.4.6
[INFO] [stderr]    Compiling parking_lot v0.12.5
[INFO] [stderr]    Compiling indoc v1.0.9
[INFO] [stderr]    Compiling unindent v0.1.11
[INFO] [stderr]    Compiling axum-macros v0.3.8
[INFO] [stderr]    Compiling base64 v0.21.7
[INFO] [stderr]    Compiling pyo3-build-config v0.19.2
[INFO] [stderr]    Compiling idna_adapter v1.2.1
[INFO] [stderr]    Compiling tracing v0.1.44
[INFO] [stderr]    Compiling idna v1.1.0
[INFO] [stderr]    Compiling pin-project v1.1.11
[INFO] [stderr]    Compiling url v2.5.8
[INFO] [stderr]    Compiling pyo3-ffi v0.19.2
[INFO] [stderr]    Compiling pyo3 v0.19.2
[INFO] [stderr]    Compiling pyo3-macros-backend v0.19.2
[INFO] [stderr]    Compiling serde_path_to_error v0.1.20
[INFO] [stderr]    Compiling pyo3-asyncio-macros v0.19.0
[INFO] [stderr]    Compiling serde_urlencoded v0.7.1
[INFO] [stderr]    Compiling futures-executor v0.3.32
[INFO] [stderr]    Compiling futures v0.3.32
[INFO] [stderr]    Compiling ppv-lite86 v0.2.21
[INFO] [stderr]    Compiling tower v0.4.13
[INFO] [stderr]    Compiling hyper v0.14.32
[INFO] [stderr]    Compiling rand_chacha v0.3.1
[INFO] [stderr]    Compiling rand v0.8.5
[INFO] [stderr]    Compiling pyo3-macros v0.19.2
[INFO] [stderr]    Compiling tungstenite v0.20.1
[INFO] [stderr]    Compiling tokio-tungstenite v0.20.1
[INFO] [stderr]    Compiling pyo3-asyncio v0.19.0
[INFO] [stderr]    Compiling hypermangle-py v0.2.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | create_exception!(hypermangle_py, ClosedWebSocket, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | create_exception!(hypermangle_py, ClosedWebSocket, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | create_exception!(hypermangle_py, WebSocketError, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | create_exception!(hypermangle_py, WebSocketError, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:18:1
[INFO] [stdout]    |
[INFO] [stdout] 18 | create_exception!(hypermangle_py, NotYetAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:18:1
[INFO] [stdout]    |
[INFO] [stdout] 18 | create_exception!(hypermangle_py, NotYetAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | create_exception!(hypermangle_py, AlreadyAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | create_exception!(hypermangle_py, AlreadyAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: feature `exclusive_wrapper` is declared but not used
[INFO] [stdout]  --> src/lib.rs:1:12
[INFO] [stdout]   |
[INFO] [stdout] 1 | #![feature(exclusive_wrapper)]
[INFO] [stdout]   |            ^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_features)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 32.62s
[INFO] running `Command { std: "docker" "inspect" "3cecbd1be65ab260256e7a410067230380ab00c9a5ad171ebd4a2950936198af", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "3cecbd1be65ab260256e7a410067230380ab00c9a5ad171ebd4a2950936198af", kill_on_drop: false }`
[INFO] [stdout] 3cecbd1be65ab260256e7a410067230380ab00c9a5ad171ebd4a2950936198af
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+0abe69e6c16114311cc2700e972492e64d69c28f" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] c2aef31695dd1a7f4e614f158ee682e143ce3d78d885c4152e659e5d23737a69
[INFO] running `Command { std: "docker" "start" "-a" "c2aef31695dd1a7f4e614f158ee682e143ce3d78d885c4152e659e5d23737a69", kill_on_drop: false }`
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | create_exception!(hypermangle_py, ClosedWebSocket, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling hypermangle-py v0.2.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | create_exception!(hypermangle_py, ClosedWebSocket, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | create_exception!(hypermangle_py, WebSocketError, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | create_exception!(hypermangle_py, WebSocketError, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:18:1
[INFO] [stdout]    |
[INFO] [stdout] 18 | create_exception!(hypermangle_py, NotYetAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:18:1
[INFO] [stdout]    |
[INFO] [stdout] 18 | create_exception!(hypermangle_py, NotYetAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | create_exception!(hypermangle_py, AlreadyAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | create_exception!(hypermangle_py, AlreadyAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: feature `exclusive_wrapper` is declared but not used
[INFO] [stdout]  --> src/lib.rs:1:12
[INFO] [stdout]   |
[INFO] [stdout] 1 | #![feature(exclusive_wrapper)]
[INFO] [stdout]   |            ^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_features)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | create_exception!(hypermangle_py, ClosedWebSocket, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | create_exception!(hypermangle_py, ClosedWebSocket, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | create_exception!(hypermangle_py, WebSocketError, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | create_exception!(hypermangle_py, WebSocketError, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:18:1
[INFO] [stdout]    |
[INFO] [stdout] 18 | create_exception!(hypermangle_py, NotYetAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:18:1
[INFO] [stdout]    |
[INFO] [stdout] 18 | create_exception!(hypermangle_py, NotYetAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | create_exception!(hypermangle_py, AlreadyAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/lib.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | create_exception!(hypermangle_py, AlreadyAccepted, pyo3::exceptions::PyException);
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: feature `exclusive_wrapper` is declared but not used
[INFO] [stdout]  --> src/lib.rs:1:12
[INFO] [stdout]   |
[INFO] [stdout] 1 | #![feature(exclusive_wrapper)]
[INFO] [stdout]   |            ^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_features)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 1.55s
[INFO] running `Command { std: "docker" "inspect" "c2aef31695dd1a7f4e614f158ee682e143ce3d78d885c4152e659e5d23737a69", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c2aef31695dd1a7f4e614f158ee682e143ce3d78d885c4152e659e5d23737a69", kill_on_drop: false }`
[INFO] [stdout] c2aef31695dd1a7f4e614f158ee682e143ce3d78d885c4152e659e5d23737a69
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+0abe69e6c16114311cc2700e972492e64d69c28f" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] ea5bcb02cff08fb6995db19ead53b97300fc7249faddda7a796261aa925987ce
[INFO] running `Command { std: "docker" "start" "-a" "ea5bcb02cff08fb6995db19ead53b97300fc7249faddda7a796261aa925987ce", kill_on_drop: false }`
[INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stderr]   --> src/lib.rs:16:1
[INFO] [stderr]    |
[INFO] [stderr] 16 | create_exception!(hypermangle_py, ClosedWebSocket, pyo3::exceptions::PyException);
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stderr]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stderr]   --> src/lib.rs:16:1
[INFO] [stderr]    |
[INFO] [stderr] 16 | create_exception!(hypermangle_py, ClosedWebSocket, pyo3::exceptions::PyException);
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stderr]   --> src/lib.rs:17:1
[INFO] [stderr]    |
[INFO] [stderr] 17 | create_exception!(hypermangle_py, WebSocketError, pyo3::exceptions::PyException);
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stderr]   --> src/lib.rs:18:1
[INFO] [stderr]    |
[INFO] [stderr] 18 | create_exception!(hypermangle_py, NotYetAccepted, pyo3::exceptions::PyException);
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stderr]   --> src/lib.rs:19:1
[INFO] [stderr]    |
[INFO] [stderr] 19 | create_exception!(hypermangle_py, AlreadyAccepted, pyo3::exceptions::PyException);
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: feature `exclusive_wrapper` is declared but not used
[INFO] [stderr]  --> src/lib.rs:1:12
[INFO] [stderr]   |
[INFO] [stderr] 1 | #![feature(exclusive_wrapper)]
[INFO] [stderr]   |            ^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: `#[warn(unused_features)]` (part of `#[warn(unused)]`) on by default
[INFO] [stderr] 
[INFO] [stderr] warning: `hypermangle-py` (lib) generated 9 warnings (3 duplicates)
[INFO] [stderr] warning: `hypermangle-py` (lib test) generated 9 warnings (9 duplicates)
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.23s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/hypermangle_py-6fbb71a01039f0a7)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests hypermangle_py
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] running `Command { std: "docker" "inspect" "ea5bcb02cff08fb6995db19ead53b97300fc7249faddda7a796261aa925987ce", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "ea5bcb02cff08fb6995db19ead53b97300fc7249faddda7a796261aa925987ce", kill_on_drop: false }`
[INFO] [stdout] ea5bcb02cff08fb6995db19ead53b97300fc7249faddda7a796261aa925987ce
